this seems pretty long 😅, I'm working on rendering the RFCs in the docs website, depending on frontmatter support or other formats I would love to use something like that

Not sure how the length of the RFC would affect how we render things?

that comment has two points:

1. The format here matters because we want it to render well in the docs website
2. I'm not sure a lengthy template is the way to start

take a look at #6, that's roughly how proposals should be formatted

actually lets merge #7 first

@AdamGS I'm not sure how the formatting of the current template is special? It looks like normal markdown to me (other than the header).

Also, I would far prefer a lengthy template to a short one because it gives the writer an idea of how to structure it. We don't necessarily have to require everyone to follow the exact template but it should be a good starting point. Or AFAICT none of the things that we probably want RFCs on would be sufficiently described with anything less than this...

yeah I was (and now @a10y) figuring out formatting, nothing is special.

I don't really feel strongly about this template, lets ship it

how does the CI work here? Seems like the build is getting blocked.

I'll also update the header

oh I guess I don't need to make a specific header anymore?

Also when I run bun run dev it shows @AdamGS instead of me, not really sure where its coming from?

It pulls the author from git history. The user who committed the file is marked as the author.